-
Notifications
You must be signed in to change notification settings - Fork 2
Formatting #17
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Formatting #17
Conversation
|
I'm done with all my updates on my fork. Each potential PR has its own branch:
My commit history of these could be cleaned up: each of the branches are expecting a certain order rather than stand alone. I can rewrite history on request but my repo meets my needs. |
|
I guess I'm using this PR for a change log of how my fork has diverged. New feature branch named handleAll: setup/tests can't kill the runner. Mark a failure instead. Here's my raw notes dump on why the old version wasn't working and why mine does. (included in master branch) |
Hey I found your repo for testing Red. It's simple and does what I want but is outdated and has a bug. This repo is abandoned but I'm contributing changes for the sake of others. This PR has no functional change and it's purpose is to reach out to see if you'll allow some changes (and also there shouldn't be trailing spaces, I mean honestly).
In addition to this PR my fork has a few more changes:
Which are in their own branches if you want to have tiny PRs. Or you could just merge my master to your master. I haven't tagged anything. I also noticed that you have a redundant branch named "develop".
In the mean time I'll be trying to figure out how to update RedUnit to the latest version of Red.